home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Night Owl 6
/
Night Owl's Shareware - PDSI-006 - Night Owl Corp (1990).iso
/
033a
/
mxtm_10.zip
/
MAXTIME.CFG
next >
Wrap
Text File
|
1991-05-27
|
7KB
|
136 lines
;
; MaxTime configuration file
;
; All parameters oriented as single line records, terminated by usual
; carraige return/linefeed. Use standard text editor to modify. Use
; a ';' to turn off line. Maxtime will ignore anything on line record
; after it encounters a ';'. Notice that each active record begins with
; Keyword. You can move these lines to any position in file, but keyword
; itself can not be changed. Elsewise, MaxTime will ignore rest of line.
; Each token/field in record is seperated by 1 or more blanks/tab.
;
;
; Bulletin: This will display a bulletin file upon signon. The file is
; standard ascii text. Maxtime will only display the file IF
; the date of the bulletin file is newer than the last logon
; date of the user OR the user is new to Maxtime. It will
; automatically be paged to the screen if there are more than
; 23 lines of text. The filename may have a standard DOS path.
; If no drive/pathname given then file is assumed to be in the
; Maximus root directory.
;
Bulletin MaxTime.bul
;
;
; CfgFile: User Configuration file. This is a special binary file MaxTime
; uses to track user information. No pathname is used here.
; MaxTime will create file if not existing. If you wish all users
; to loose their banked time, just delete this file and MaxTime
; will restart everyone as new user. Default name is "MaxTime.usr"
; if no parameter specified.
;
CfgFile Maxtime.usr
;
;
; LogFile: Log file to track what user does while inside MaxTime. Totally
; compatable with standard Maximus/Binkley log format. You can
; even specify the standard Maximus log file if wanted. It will
; automatically append to it. Logfile is optional,but reccomended
; Any errors occuring will also be logged.
;
LogFile MaxTime.log
;
;
; NewHelpFile: Text file displayed to new user. When MaxTime can not find
; user in config file, it will first display this file to new user,
; with automatic paging every 23 lines. Do not put any control
; characters in file, but IBM text (8 bit chars) may be used.
; This file is optional, but reccomended to explain to new user
; what MaxTime is all about. Keep file short and to the point.
;
NewHelpFile Maxtime.hlp
;
;
; Colors: Tell MaxTime what colors to use where. Of course these
; colors are ONLY displayed if user has set ANSI or AVATAR
; video modes. Currently there are 6 different types of text
; attributes defined as follows:
;
;Standard Text,Hilite Text,Menu Items,Time Left,Prompt,Attention Text
;
; A standard set is included as follows. You should have all
; 6 values filled in, else it will just repeat last value
; until six items are in the color set. You will just have
; to play with these values to see which ones are applied
; to what text. I have tried to use labels that make sense
; at least to me! The local screen will always display the
; what user is seeing. Even if user is in Avatar mode, the
; local screen will display the ANSI version of the colors,
; which is the same of course but not Avatar codes.
;
; Though these tokens are in DECIMAL value, attributes
; are the standard 8 bit IBM char attributes. Upper 4 bits
; are the background (high bit is blink) and lower 3 bits are
; the foreground (I always set the intensity bit). Here are
; the standard IBM color codes:
;
; 0 Black 4 Blue
; 1 Red 5 Magenta
; 2 Green 6 Cyan
; 3 Yellow 7 White
;
; If you decide to use any background color other than black, you
; might get some messy results. Once the color is set, it will also
; paint the rest of the line and blank space UNTIL a new color is
; is set. It looks weird in most places except the TIME LEFT text
; attribute. Just a suggestion. Feel free to experiment. The local
; mode will look the same as the remote user sees it. Remember the
; values are in DECIMAL not HEX.
;
colors 06,03,02,87,04,01
;
;
; MaxTimeSession: Maximum amount of time a user may borrow in any 1 bbs
; session. Of course MaxTime is designed so it will
; NEVER allow adding any more time than any pending event
; would allow, i.e. MaxTime computes time to next event and
; won't overrun it. This is based upon the "-t" switch passed
; to Maximus at startup. Value specified here may be
; overridden by the "/MTx" switch on command line, where
; x is decimal value. Thus, you could get fancy with mecca
; and customize this on a user by user or priv level basis.
;
MaxTimeSession 30
;
;
; MaxTimeDaily: Maximum amount of time a user may borrow DAILY from the
; time bank. Daily is considered any time a user runs Maxtime
; within 24 hours of last run. As above, Maxtime will never
; give the user more time than any pending event will allow.
; If you specify 0 here, then that allows user to borrow as
; much time daily he has in the bank. Of course only so much
; can be borrowed in 1 session, as set in above parameter. If
; this parameter is not specified, a default is 60 minutes.
;
MaxTimeDaily 30
;
; MaxDepositDaily: Maximum amount of time a user may deposit DAILY into
; the time bank. Daily is considered any time a user runs
; Maxtime within 24 hours of last run. If this parameter
; is not specified, a default is 60 minutes. This value must
; always be 1 or greater.
;
MaxDepositDaily 30
;
; MaxBankSession: Maximum amount of time a user may store in any 1 bbs
; session. This value may be overridden by the "/MBx"
; switch on command line, where x is decimal value. Thus,
; you could get fancy with mecca and customize this on
; a user by user or priv level basis.
;
;
MaxBankSession 30
;